NTISthis.com

Evidence Guide: ICTPRG526 - Maintain functionality of legacy code programs

Student: __________________________________________________

Signature: _________________________________________________

Tips for gathering evidence to demonstrate your skills

The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!

From the Wiki University

 

ICTPRG526 - Maintain functionality of legacy code programs

What evidence can you provide to prove your understanding of each of the following citeria?

Determine the functional changes required

  1. Consult the user to determine, and document, the functional change required
  2. Clarify the impact of changes with operational personnel
Consult the user to determine, and document, the functional change required

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Clarify the impact of changes with operational personnel

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Review legacy language

  1. Identify the basic structures of the legacy language
  2. Review the data storage of the legacy language with regard to global variables, modularisation, cohesion and coupling
  3. Review the basic algorithms of the legacy language
Identify the basic structures of the legacy language

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Review the data storage of the legacy language with regard to global variables, modularisation, cohesion and coupling

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Review the basic algorithms of the legacy language

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Identify and isolate the change

  1. Review the technical documentation for the system, to determine which modules to change
  2. Review the source code to determine program logic and flow
  3. Update the technical documentation to reflect the current state of the program
Review the technical documentation for the system, to determine which modules to change

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Review the source code to determine program logic and flow

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Update the technical documentation to reflect the current state of the program

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Determine the framework for change

  1. Determine the change approach to be used to implement the change
  2. Ascertain and detail the risks for each approach
  3. Determine the personnel who will make the changes
Determine the change approach to be used to implement the change

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Ascertain and detail the risks for each approach

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Determine the personnel who will make the changes

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Design the change

  1. Develop the changes required, considering the impact of the changes on other parts of the system
  2. Document the changes according to change-management standards
Develop the changes required, considering the impact of the changes on other parts of the system

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document the changes according to change-management standards

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Code the change

  1. Identify and obtain, the appropriate hardware and software for the change
  2. Write the code according to programming standards
  3. Compile and unit test the changes
  4. Document the changes according to programming standards
Identify and obtain, the appropriate hardware and software for the change

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Write the code according to programming standards

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Compile and unit test the changes

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document the changes according to programming standards

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Test the change

  1. System test the changes and record the outcomes
  2. Perform user acceptance testing and record the outcomes
  3. Sign off the change request
System test the changes and record the outcomes

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Perform user acceptance testing and record the outcomes

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Sign off the change request

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Archive the system

  1. Create a new version of software, according to configuration management standards
  2. Archive the development system, including the source code, compilers and test data
Create a new version of software, according to configuration management standards

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Archive the development system, including the source code, compilers and test data

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Assessed

Teacher: ___________________________________ Date: _________

Signature: ________________________________________________

Comments:

 

 

 

 

 

 

 

 

Instructions to Assessors

Evidence Guide

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Determine the functional changes required

1.1 Consult the user to determine, and document, the functional change required

1.2 Clarify the impact of changes with operational personnel

2. Review legacy language

2.1 Identify the basic structures of the legacy language

2.2 Review the data storage of the legacy language with regard to global variables, modularisation, cohesion and coupling

2.3 Review the basic algorithms of the legacy language

3. Identify and isolate the change

3.1 Review the technical documentation for the system, to determine which modules to change

3.2 Review the source code to determine program logic and flow

3.3 Update the technical documentation to reflect the current state of the program

4. Determine the framework for change

4.1 Determine the change approach to be used to implement the change

4.2 Ascertain and detail the risks for each approach

4.3 Determine the personnel who will make the changes

5. Design the change

5.1 Develop the changes required, considering the impact of the changes on other parts of the system

5.2 Document the changes according to change-management standards

6. Code the change

6.1 Identify and obtain, the appropriate hardware and software for the change

6.2 Write the code according to programming standards

6.3 Compile and unit test the changes

6.4 Document the changes according to programming standards

7. Test the change

7.1 System test the changes and record the outcomes

7.2 Perform user acceptance testing and record the outcomes

7.3 Sign off the change request

8. Archive the system

8.1 Create a new version of software, according to configuration management standards

8.2 Archive the development system, including the source code, compilers and test data

Required Skills and Knowledge

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Determine the functional changes required

1.1 Consult the user to determine, and document, the functional change required

1.2 Clarify the impact of changes with operational personnel

2. Review legacy language

2.1 Identify the basic structures of the legacy language

2.2 Review the data storage of the legacy language with regard to global variables, modularisation, cohesion and coupling

2.3 Review the basic algorithms of the legacy language

3. Identify and isolate the change

3.1 Review the technical documentation for the system, to determine which modules to change

3.2 Review the source code to determine program logic and flow

3.3 Update the technical documentation to reflect the current state of the program

4. Determine the framework for change

4.1 Determine the change approach to be used to implement the change

4.2 Ascertain and detail the risks for each approach

4.3 Determine the personnel who will make the changes

5. Design the change

5.1 Develop the changes required, considering the impact of the changes on other parts of the system

5.2 Document the changes according to change-management standards

6. Code the change

6.1 Identify and obtain, the appropriate hardware and software for the change

6.2 Write the code according to programming standards

6.3 Compile and unit test the changes

6.4 Document the changes according to programming standards

7. Test the change

7.1 System test the changes and record the outcomes

7.2 Perform user acceptance testing and record the outcomes

7.3 Sign off the change request

8. Archive the system

8.1 Create a new version of software, according to configuration management standards

8.2 Archive the development system, including the source code, compilers and test data

Evidence of the ability to:

read legacy language

identify and isolate the required change

implement the change via the chosen technique.

Note: If a specific volume or frequency is not stated, then evidence must be provided at least once.

To complete the unit requirements safely and effectively, the individual must:

explain operational procedures on the required operating system

outline the organisational standards for software development

define security and viruses

identify privacy legislation and copyright with regard to the legacy code, the particular system involved and its data

define the technical terminology related to reading help files and manuals

outline different types of software.